Use float
instead of double
for altitudeAngle
and azimuthAngle
#485
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Altitude angle and azimuth angle are computed always computed with 32-bit floating points. For example, on macOS, https://developer.apple.com/documentation/appkit/nsevent/1534226-tilt. A priori, using a double doesn't offer more precision.
[EDIT: On macOS, the NSPoint struct uses
double
when the OS is x64, so this implies double accuracy is correct]Preview | Diff